Skip to content

Moving FSL into riscv-perf-model #263

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

klingaard
Copy link
Collaborator

The software package "Fusion/Fracture Specification Language" written by Jeff Nye (@jeffnye-gh) was
provided to the RISC-V Performance Modeling SIG under the Apache License 2.0 agreement
as a submodule (fsl) to riscv-perf-model GitHub repo.

Having such a dependency exposes unintended consequences where the original author can, at any juncture, remove access to that submodule thus inhibiting, if not halting, development within this SIG.

In addition, updates/changes to this dependency must go through the original author thus potentially delaying
progress of riscv-perf-model development.

This PR copies the fsl submodule directly into the riscv-perf-model GitHub repository and removes the external
dependency. Specifically, section 4 of the Apache 2.0 License agreement, provided in the original FSL distribution states:

  1. Redistribution. You may reproduce and distribute copies of the
    Work or Derivative Works thereof in any medium, with or without
    modifications, and in Source or Object form

In addition, to adhere to section 4b:

(b) You must cause any modified files to carry prominent notices
stating that You changed the files

The FSL library was copied as is without modification and therefore does not contain any additional
prominent notices.

@klingaard klingaard requested a review from arupc July 6, 2025 22:56
@klingaard klingaard self-assigned this Jul 6, 2025
@klingaard
Copy link
Collaborator Author

During our meeting on July 7th, 2025, @rajatbhatia1 had a good idea to investigate forking submodules like fsl, stflib and mavis directly into the RISC-V software GitHub environment. That way, if/when the original authors update their submodules, we can move Olympia forward as necessary. In addition, if the original fork moves or is no longer supported, Olympia can still make forward progress.

@arupc will investigate how we can do this, and if we can make that happen, I'll close this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants